MAS V3.4 PTF03 Function Reference
The following functions are being shipped on the 2216 in MAS V3.4 PTF03, so they are available in that level and in all subsequent maintenance levels of MAS V3.4. This document contains the 2216 publications updates for these new functions. For information about installing this PTF, refer to the "Introduction and General Download Instructions" document available on the 2216 Operational Code web page.
| Note: | If you install this PTF or any subsequent MAS V3.4 PTF, you need to upgrade your V3.4 Configuration Program to PTF NP01150 or later. The V3.4 Configuration program is available on the 2216 Configuration Program web page. |
These functions include:
Refer to www.networking.ibm.com/support for a copy of this Function Reference as well as the 2216 base publications.
With this PTF, you can ensure every http request forwarded to a back-end server contains a Client-IP address header. This will allow back-end servers to know the origin of every http request. Web Server Cache will insert a Client-IP address header into every http request that is forwarded to a back-end server. The Client-IP address header contains the source (client) IP address of the TCP connection received by Web Server Cache. If an http request already has a Client-IP address header, the Web Server Cache passes the http request to the back-end server unchanged.
To enable this function (disabled is the default), use the Talk 6 patch command to change the variable webc-client-ip to any non-zero value as follows:
Config>patch Variable to patch ?[] webc-client-ip New Value [0]? 1 Variable patched successfully Config>
To stop adding Client-IP address headers, use the patch command to change the variable back to zero:
Config>patch Variable to patch ?[] webc-client-ip New Value [1]? 0 Variable patched successfully Config>
Two new ELS messages have been added for this function:
WEBH.021 C-INFO Client-IP addr hdr present
WEBH.022 C-INFO Client-IP addr hdr added
When the Client-IP address header is added, it is added immediately after the CRLF that ends the request-line portion of the http header.
With this PTF in a WAN reroute configuration, if a primary connection is restored outside the revert back window, both the primary and alternate circuits are allowed to remain up until the revert back window is reached, at which time the alternate connection is ended. This allows IP traffic and new SNA sessions to use the primary circuit immediately when a connection is restored outside the revert back window. SNA sessions that were established over the alternate circuit are not affected until the revert back window is reached.
Using the Talk 6 patch command, you can disable WAN Reroute Revert Back Enhancement (enabled is the default). To disable this function, use the patch command to change the variable wrr-delay-pup to any non-zero value as follows:
Config>patch Variable to patch ?[] wrr-delay-pup New Value [0]? 1 Variable patched successfully Config>
To re-enable the WAN Reroute Revert Back Enhancement, use the patch command to change the variable back to zero:
Config>patch Variable to patch ?[] wrr-delay-pup New Value [1]? 0 Variable patched successfully Config>
With this PTF, the existing APPN MIB implementation is updated with the current RFC (RCF2455) for that MIB. This new MIB contains the six new objects that were added with RCF2455. One object was removed from the MIB. The following new objects were added to the APPN MIB:
The following object was removed from the APPN MIB: